vSphere to Google Drive Manual Migration Runbook

End-to-End Operational Documentation & Commands

Host Platform: Apple Silicon Mac Studio (M4 / ARM64 Native)

Executive Summary

This runbook describes the successful methodology used to manually migrate, back up, and purge infrastructure assets from a VMware vSphere ecosystem (10.11.11.13) directly to cold cloud storage. By executing native ARM64 tools on the target host Mac Studio, network translation abstraction layers are avoided, allowing optimal stream throughput across the local interface network block.

Step 1: Setup Infrastructure Environment variables

Before launching queries or transfers, parameters must be exported into the shell session. Special handling is implemented via single quotes to cleanly escape shell history expansion syntax characters (such as !) in target secrets.

Terminal Environment Variables

export GOVC_URL="10.11.11.13"
export GOVC_USERNAME="Administrator@VSPHERE.LOCAL"
export GOVC_PASSWORD='TDN1hzg7xth0fmh!xwh'
export GOVC_INSECURE="true"

Step 2: Initialize Infrastructure Discovery & Integrity Check

Pre-verification ensures the vSphere API handshake completes seamlessly, and dynamically isolates target VM assets that are currently powered down and safe for replication.

Verification Commands

# Verify global infrastructure connectivity parameters
govc about

# Query cluster footprint for poweredOff target nodes
govc find . -type m -runtime.powerState poweredOff

Step 3: Storage Mapping & Capacity Pre-flight Check

To avoid local volume overflow, the target disk block footprint must be validated against local storage volumes on the Mac Studio before invoking download pipes.

Capacity Validation Checks

# Query absolute free blocks on Mac Studio Downloads storage mount
echo "Mac Studio Free Space: $(df -g ~/Downloads | awk 'NR==2 {print $4}') GB"

# Fetch explicit allocated/committed storage footprint metrics for target VM
govc vm.info -r "/SECUNETICS/vm/CORP_IT/AWX02" | grep -E "Memory|Storage"

Step 4: Execute Optimized OVF Stream Extraction

The standard vSphere management network client uses an HTTP/2 protocol stream loop scheduler that can artificially throttle migration bandwidth blocks. Prepending the Go debugging allocator environment flag (GODEBUG=http2client=0) forces the client down to an unthrottled HTTP/1.1 channel, significantly increasing read performance.

Throttling-Bypass Export

# Create local scratch drive landing block partition
mkdir -p ~/Downloads/vsphere_scratch

# Invoke unthrottled asynchronous OVF metadata and VMDK block extraction
GODEBUG=http2client=0 govc export.ovf -vm "/SECUNETICS/vm/CORP_IT/AWX02" ~/Downloads/vsphere_scratch/

Thin-Provisioned Transfer Mechanics

During the export sequence, throughput read indicators may intermittently drop to 0B/s. This indicates optimal operation where the thin-provisioning engine is automatically skipping non-allocated sparse system geometry, resulting in zero consumption of local network resources.

Step 5: Offload Stream to Google Cloud Storage & Auto-Purge

Using the custom Google App Client ID configuration endpoint, the extracted workspace payload is moved to the target directory cloud root. The move operand completely sanitizes and purges the scratch drive sector locally the exact second the cloud upload completes successfully.

Cloud Synchronization

# Sync payload block structure directly with progress flag tracking enabled
rclone move ~/Downloads/vsphere_scratch/ gdrive:vsphere_backup/AWX02/ --drive-chunk-size 64M -P

# Post-Execution Check: Confirm local scratch workspace directory blocks are clear
ls -la ~/Downloads/vsphere_scratch/

Step 6: Decommission Source Machine Asset

Once data synchronization is completed and verified on Google Drive, the source node can be decommissioned from production inventories. The vm.destroy command issues a terminal deletion sequence that clears the target registration and wipes all underlying system virtual disks entirely from the datastore array.

CRITICAL DESTRUCTIVE OPERATION

This instruction unrecoverably removes raw data blocks from production arrays. Confirm backup validation parameters are fully verified inside Google Drive before execution.

vSphere Wiping Sequence

govc vm.destroy "/SECUNETICS/vm/CORP_IT/AWX02"